Sidelink discontinuous reception configuration

ABSTRACT

Apparatuses, methods, and systems are disclosed for sidlink discontinuous reception configuration. One method (1000) includes accessing (1002) a sidelink discontinuous reception configuration. The sidelink discontinuous reception configuration corresponds to a quality of service class; an identifier of the quality of service class; at least on attribute of the quality of service class; or some combination thereof. The method (1000) includes performing (1004) sidelink communication based on the sidelink discontinuous reception configuration.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Patent Application Ser. No.63/051,184 entitled “APPARATUSES, METHODS, AND SYSTEMS FORA SIDELINK DRXMECHANISM-INTERACTION WITH UU DRX OPERATION” and filed on Jul. 13, 2020for Joachim Loehr, U.S. Patent Application Ser. No. 63/051,207 entitled“APPARATUSES, METHODS, AND SYSTEMS FOR SIDELINK POWER SAVING USING A DRXMECHANISM AND MINIMIZING ENSUING HALF DUPLEX ISSUES” and filed on Jul.13, 2020 for Prateek Basu Mallick, U.S. Patent Application Ser. No.63/051,217 entitled “APPARATUSES, METHODS, AND SYSTEMS FOR SUPPORTINGPOWER SAVING FOR PC5 COMMUNICATIONS” and filed on Jul. 13, 2020 forDimitrios Karampatsis, and U.S. Patent Application Ser. No. 63/051,233entitled “APPARATUSES, METHODS, AND SYSTEMS FOR ENHANCEMENT FOR SL POWERSAVING” and filed on Jul. 13, 2020 for Karthikeyan Ganesan, all of whichare incorporated herein by reference in their entirety.

FIELD

The subject matter disclosed herein relates generally to wirelesscommunications and more particularly relates to sidelink discontinuousreception configuration.

BACKGROUND

In certain wireless communications networks, a configuration forsidelink discontinuous reception may be inefficient. A sidelinkdiscontinuous reception configuration may be updated and/or provided toa user equipment.

BRIEF SUMMARY

Methods for sidelink discontinuous reception configuration aredisclosed. Apparatuses and systems also perform the functions of themethods. One embodiment of a method includes accessing a sidelinkdiscontinuous reception configuration. The sidelink discontinuousreception configuration corresponds to: a quality of service class; anidentifier of the quality of service class; at least one attribute ofthe quality of service class; a range corresponding to the at least oneattribute of the quality of service class; or some combination thereof.In some embodiments, the method includes performing sidelinkcommunication based on the sidelink discontinuous receptionconfiguration.

One apparatus for sidelink discontinuous reception configurationincludes a processor that: accesses a sidelink discontinuous receptionconfiguration, wherein the sidelink discontinuous receptionconfiguration corresponds to: a quality of service class; an identifierof the quality of service class; at least one attribute of the qualityof service class; a range corresponding to the at least one attribute ofthe quality of service class; or some combination thereof; and performssidelink communication based on the sidelink discontinuous receptionconfiguration.

Another embodiment of a method for sidelink discontinuous receptionconfiguration includes determining, at a first user equipment, at leastone parameter for a sidelink discontinuous reception configuration. Insome embodiments, the method includes transmitting the at least oneparameter for the sidelink discontinuous reception configuration to asecond user equipment. In certain embodiments, the method includesreceiving feedback from the second user equipment indicating acceptanceof the at least one parameter for the sidelink discontinuous receptionconfiguration.

Another apparatus for sidelink discontinuous reception configurationincludes a first user equipment. In some embodiments, the apparatusincludes a processor that determines at least one parameter for asidelink discontinuous reception configuration. In various embodiments,the apparatus includes a transmitter that transmits the at least oneparameter for the sidelink discontinuous reception configuration to asecond user equipment. In certain embodiments, the apparatus includes areceiver that receives feedback from the second user equipmentindicating acceptance of the at least one parameter for the sidelinkdiscontinuous reception configuration.

Yet another embodiment of a method for sidelink discontinuous receptionconfiguration includes accessing a sidelink discontinuous receptionconfiguration. The sidelink discontinuous reception configurationincludes a first offset for an on-duration, an on-duration timer, and aperiodicity. In some embodiments, the method includes determining asecond offset for the on-duration. In certain embodiments, the methodincludes transmitting data based on the sidelink discontinuous receptionconfiguration and the second offset for the on-duration.

Yet another apparatus for sidelink discontinuous reception configurationincludes a processor that: accesses a sidelink discontinuous receptionconfiguration, wherein the sidelink discontinuous receptionconfiguration comprises a first offset for an on-duration, anon-duration timer, and a periodicity; and determines a second offset forthe on-duration. In various embodiments, the apparatus includes atransmitter that transmits data based on the sidelink discontinuousreception configuration and the second offset for the on-duration.

A further embodiment of a method for sidelink discontinuous receptionconfiguration includes accessing a sidelink discontinuous receptionconfiguration. The sidelink discontinuous reception configurationincludes an offset for an on-duration, an on-duration timer, and aperiodicity. In some embodiments, the method includes transmittingsidelink data, receiving the sidelink data, or a combination thereof. Incertain embodiments, the method includes, in response to transmittingthe sidelink data, receiving the sidelink data, or a combinationthereof, starting a sidelink inactivity timer. In various embodiments,the method includes restarting the sidelink inactivity timer in responseto: indicating a negative acknowledgement on a physical uplink controlchannel to request a retransmission grant to a base station; indicatingan acknowledgement on the physical uplink control channel and inresponse to having a non-empty sidelink buffer to the base station;receiving hybrid automatic repeat request feedback on a physicalsidelink feedback channel from a sidelink receiver user equipment;transmitting a sidelink scheduling request to a base station;transmitting a sidelink buffer status report to the base station;requesting a channel state information report on sidelink from a peeruser equipment; receiving a request for a channel state informationreport on sidelink from a peer user equipment; receiving sidelinkcontrol information from the sidelink transmitter user equipment;receiving data from the sidelink transmitter user equipment;transmitting a physical sidelink feedback channel negativeacknowledgement feedback to the sidelink transmitter user equipment;transmitting sidelink control information requesting sidelink physicalsidelink feedback channel feedback; transmitting non-last sidelinkcontrol information while performing blind re-transmissions;transmitting non-last data while performing blind re-transmissions; async source using a value of a sidelink inactivity timer greater than apredetermined value; or some combination thereof.

A further apparatus for sidelink discontinuous reception configurationincludes a processor that accesses a sidelink discontinuous receptionconfiguration. The sidelink discontinuous reception configurationincludes an offset for an on-duration, an on-duration timer, and aperiodicity. In various embodiments, the apparatus includes atransmitter. In certain embodiments, the apparatus includes a receiver.The transmitter transmits sidelink data, the receiver receives thesidelink data, or a combination thereof. In response to the transmittertransmitting sidelink data, the receiver receiving the sidelink data, ora combination thereof, the processor starts a sidelink inactivity timer.The processor restarts the sidelink inactivity timer in response to:indicating a negative acknowledgement on a physical uplink controlchannel to request a retransmission grant to a base station; indicatingan acknowledgement on the physical uplink control channel and inresponse to having a non-empty sidelink buffer to the base station;receiving hybrid automatic repeat request feedback on a physicalsidelink feedback channel from a sidelink receiver user equipment;transmitting a sidelink scheduling request to a base station;transmitting a sidelink buffer status report to the base station;requesting a channel state information report on sidelink from a peeruser equipment; receiving a request for a channel state informationreport on sidelink from a peer user equipment; receiving sidelinkcontrol information from the sidelink transmitter user equipment;receiving data from the sidelink transmitter user equipment;transmitting a physical sidelink feedback channel negativeacknowledgement feedback to the sidelink transmitter user equipment;transmitting sidelink control information requesting sidelink physicalsidelink feedback channel feedback; transmitting non-last sidelinkcontrol information while performing blind re-transmissions;transmitting non-last data while performing blind re-transmissions; async source using a value of a sidelink inactivity timer greater than apredetermined value; or some combination thereof.

BRIEF DESCRIPTION OF THE DRAWINGS

A more particular description of the embodiments briefly described abovewill be rendered by reference to specific embodiments that areillustrated in the appended drawings. Understanding that these drawingsdepict only some embodiments and are not therefore to be considered tobe limiting of scope, the embodiments will be described and explainedwith additional specificity and detail through the use of theaccompanying drawings, in which:

FIG. 1 is a schematic block diagram illustrating one embodiment of awireless communication system for sidelink discontinuous receptionconfiguration;

FIG. 2 is a schematic block diagram illustrating one embodiment of anapparatus that may be used for sidelink discontinuous receptionconfiguration;

FIG. 3 is a schematic block diagram illustrating one embodiment of anapparatus that may be used for sidelink discontinuous receptionconfiguration;

FIG. 4 is a timing diagram illustrating one embodiment of a SL DRXconfiguration;

FIG. 5 is a timing diagram illustrating one embodiment of two SL DRXconfigurations corresponding to a first PQI range and a second PQIrange;

FIG. 6 is a network communications diagram illustrating one embodimentof a negotiation of SL DRX configuration for unicast communication;

FIG. 7 is a network communications diagram illustrating one embodimentof a negotiation of SL DRX configuration for groupcast communication;

FIG. 8 is a network communications diagram illustrating one embodimentof Uu negotiation to align Uu and SL DRX;

FIG. 9 is a timing diagram illustrating one embodiment of SL DRXinterplay with timers;

FIG. 10 is a flow chart diagram illustrating one embodiment of a methodfor sidelink discontinuous reception configuration;

FIG. 11 is a flow chart diagram illustrating another embodiment of amethod for sidelink discontinuous reception configuration;

FIG. 12 is a flow chart diagram illustrating yet another embodiment of amethod for sidelink discontinuous reception configuration; and

FIG. 13 is a flow chart diagram illustrating a further embodiment of amethod for sidelink discontinuous reception configuration.

DETAILED DESCRIPTION

As will be appreciated by one skilled in the art, aspects of theembodiments may be embodied as a system, apparatus, method, or programproduct. Accordingly, embodiments may take the form of an entirelyhardware embodiment, an entirely software embodiment (includingfirmware, resident software, micro-code, etc.) or an embodimentcombining software and hardware aspects that may all generally bereferred to herein as a “circuit,” “module” or “system.” Furthermore,embodiments may take the form of a program product embodied in one ormore computer readable storage devices storing machine readable code,computer readable code, and/or program code, referred hereafter as code.The storage devices may be tangible, non-transitory, and/ornon-transmission. The storage devices may not embody signals. In acertain embodiment, the storage devices only employ signals foraccessing code.

Certain of the functional units described in this specification may belabeled as modules, in order to more particularly emphasize theirimplementation independence. For example, a module may be implemented asa hardware circuit comprising custom very-large-scale integration(“VLSI”) circuits or gate arrays, off-the-shelf semiconductors such aslogic chips, transistors, or other discrete components. A module mayalso be implemented in programmable hardware devices such as fieldprogrammable gate arrays, programmable array logic, programmable logicdevices or the like.

Modules may also be implemented in code and/or software for execution byvarious types of processors. An identified module of code may, forinstance, include one or more physical or logical blocks of executablecode which may, for instance, be organized as an object, procedure, orfunction. Nevertheless, the executables of an identified module need notbe physically located together, but may include disparate instructionsstored in different locations which, when joined logically together,include the module and achieve the stated purpose for the module.

Indeed, a module of code may be a single instruction, or manyinstructions, and may even be distributed over several different codesegments, among different programs, and across several memory devices.Similarly, operational data may be identified and illustrated hereinwithin modules, and may be embodied in any suitable form and organizedwithin any suitable type of data structure. The operational data may becollected as a single data set, or may be distributed over differentlocations including over different computer readable storage devices.Where a module or portions of a module are implemented in software, thesoftware portions are stored on one or more computer readable storagedevices.

Any combination of one or more computer readable medium may be utilized.The computer readable medium may be a computer readable storage medium.The computer readable storage medium may be a storage device storing thecode. The storage device may be, for example, but not limited to, anelectronic, magnetic, optical, electromagnetic, infrared, holographic,micromechanical, or semiconductor system, apparatus, or device, or anysuitable combination of the foregoing.

More specific examples (a non-exhaustive list) of the storage devicewould include the following: an electrical connection having one or morewires, a portable computer diskette, a hard disk, a random access memory(“RAM”), a read-only memory (“ROM”), an erasable programmable read-onlymemory (“EPROM” or Flash memory), a portable compact disc read-onlymemory (“CD-ROM”), an optical storage device, a magnetic storage device,or any suitable combination of the foregoing. In the context of thisdocument, a computer readable storage medium may be any tangible mediumthat can contain, or store a program for use by or in connection with aninstruction execution system, apparatus, or device.

Code for carrying out operations for embodiments may be any number oflines and may be written in any combination of one or more programminglanguages including an object oriented programming language such asPython, Ruby, Java, Smalltalk, C++, or the like, and conventionalprocedural programming languages, such as the “C” programming language,or the like, and/or machine languages such as assembly languages. Thecode may execute entirely on the user's computer, partly on the user'scomputer, as a stand-alone software package, partly on the user'scomputer and partly on a remote computer or entirely on the remotecomputer or server. In the latter scenario, the remote computer may beconnected to the user's computer through any type of network, includinga local area network (“LAN”) or a wide area network (“WAN”), or theconnection may be made to an external computer (for example, through theInternet using an Internet Service Provider).

Reference throughout this specification to “one embodiment,” “anembodiment,” or similar language means that a particular feature,structure, or characteristic described in connection with the embodimentis included in at least one embodiment. Thus, appearances of the phrases“in one embodiment,” “in an embodiment,” and similar language throughoutthis specification may, but do not necessarily, all refer to the sameembodiment, but mean “one or more but not all embodiments” unlessexpressly specified otherwise. The terms “including,” “comprising,”“having,” and variations thereof mean “including but not limited to,”unless expressly specified otherwise. An enumerated listing of itemsdoes not imply that any or all of the items are mutually exclusive,unless expressly specified otherwise. The terms “a,” “an,” and “the”also refer to “one or more” unless expressly specified otherwise.

Furthermore, the described features, structures, or characteristics ofthe embodiments may be combined in any suitable manner. In the followingdescription, numerous specific details are provided, such as examples ofprogramming, software modules, user selections, network transactions,database queries, database structures, hardware modules, hardwarecircuits, hardware chips, etc., to provide a thorough understanding ofembodiments. One skilled in the relevant art will recognize, however,that embodiments may be practiced without one or more of the specificdetails, or with other methods, components, materials, and so forth. Inother instances, well-known structures, materials, or operations are notshown or described in detail to avoid obscuring aspects of anembodiment.

Aspects of the embodiments are described below with reference toschematic flowchart diagrams and/or schematic block diagrams of methods,apparatuses, systems, and program products according to embodiments. Itwill be understood that each block of the schematic flowchart diagramsand/or schematic block diagrams, and combinations of blocks in theschematic flowchart diagrams and/or schematic block diagrams, can beimplemented by code. The code may be provided to a processor of ageneral purpose computer, special purpose computer, or otherprogrammable data processing apparatus to produce a machine, such thatthe instructions, which execute via the processor of the computer orother programmable data processing apparatus, create means forimplementing the functions/acts specified in the schematic flowchartdiagrams and/or schematic block diagrams block or blocks.

The code may also be stored in a storage device that can direct acomputer, other programmable data processing apparatus, or other devicesto function in a particular manner, such that the instructions stored inthe storage device produce an article of manufacture includinginstructions which implement the function/act specified in the schematicflowchart diagrams and/or schematic block diagrams block or blocks.

The code may also be loaded onto a computer, other programmable dataprocessing apparatus, or other devices to cause a series of operationalsteps to be performed on the computer, other programmable apparatus orother devices to produce a computer implemented process such that thecode which execute on the computer or other programmable apparatusprovide processes for implementing the functions/acts specified in theflowchart and/or block diagram block or blocks.

The schematic flowchart diagrams and/or schematic block diagrams in theFigures illustrate the architecture, functionality, and operation ofpossible implementations of apparatuses, systems, methods and programproducts according to various embodiments. In this regard, each block inthe schematic flowchart diagrams and/or schematic block diagrams mayrepresent a module, segment, or portion of code, which includes one ormore executable instructions of the code for implementing the specifiedlogical function(s).

It should also be noted that, in some alternative implementations, thefunctions noted in the block may occur out of the order noted in theFigures. For example, two blocks shown in succession may, in fact, beexecuted substantially concurrently, or the blocks may sometimes beexecuted in the reverse order, depending upon the functionalityinvolved. Other steps and methods may be conceived that are equivalentin function, logic, or effect to one or more blocks, or portionsthereof, of the illustrated Figures.

Although various arrow types and line types may be employed in theflowchart and/or block diagrams, they are understood not to limit thescope of the corresponding embodiments. Indeed, some arrows or otherconnectors may be used to indicate only the logical flow of the depictedembodiment. For instance, an arrow may indicate a waiting or monitoringperiod of unspecified duration between enumerated steps of the depictedembodiment. It will also be noted that each block of the block diagramsand/or flowchart diagrams, and combinations of blocks in the blockdiagrams and/or flowchart diagrams, can be implemented by specialpurpose hardware-based systems that perform the specified functions oracts, or combinations of special purpose hardware and code.

The description of elements in each figure may refer to elements ofproceeding figures. Like numbers refer to like elements in all figures,including alternate embodiments of like elements.

FIG. 1 depicts an embodiment of a wireless communication system 100 forsidelink discontinuous reception configuration. In one embodiment, thewireless communication system 100 includes remote units 102 and networkunits 104. Even though a specific number of remote units 102 and networkunits 104 are depicted in FIG. 1 , one of skill in the art willrecognize that any number of remote units 102 and network units 104 maybe included in the wireless communication system 100.

In one embodiment, the remote units 102 may include computing devices,such as desktop computers, laptop computers, personal digital assistants(“PDAs”), tablet computers, smart phones, smart televisions (e.g.,televisions connected to the Internet), set-top boxes, game consoles,security systems (including security cameras), vehicle on-boardcomputers, network devices (e.g., routers, switches, modems), aerialvehicles, drones, or the like. In some embodiments, the remote units 102include wearable devices, such as smart watches, fitness bands, opticalhead-mounted displays, or the like. Moreover, the remote units 102 maybe referred to as subscriber units, mobiles, mobile stations, users,terminals, mobile terminals, fixed terminals, subscriber stations, UE,user terminals, a device, or by other terminology used in the art. Theremote units 102 may communicate directly with one or more of thenetwork units 104 via UL communication signals. In certain embodiments,the remote units 102 may communicate directly with other remote units102 via sidelink communication.

The network units 104 may be distributed over a geographic region. Incertain embodiments, a network unit 104 may also be referred to and/ormay include one or more of an access point, an access terminal, a base,a base station, a location server, a core network (“CN”), a radionetwork entity, a Node-B, an evolved node-B (“eNB”), a 5G node-B(“gNB”), a Home Node-B, a relay node, a device, a core network, anaerial server, a radio access node, an access point (“AP”), new radio(“NR”), a network entity, an access and mobility management function(“AMF”), a unified data management (“UDM”), a unified data repository(“UDR”), a UDM/UDR, a policy control function (“PCF”), a radio accessnetwork (“RAN”), a network slice selection function (“NSSF”), anoperations, administration, and management (“OAM”), a session managementfunction (“SMF”), a user plane function (“UPF”), an applicationfunction, an authentication server function (“AUSF”), security anchorfunctionality (“SEAF”), trusted non-3GPP gateway function (“TNGF”), orby any other terminology used in the art. The network units 104 aregenerally part of a radio access network that includes one or morecontrollers communicably coupled to one or more corresponding networkunits 104. The radio access network is generally communicably coupled toone or more core networks, which may be coupled to other networks, likethe Internet and public switched telephone networks, among othernetworks. These and other elements of radio access and core networks arenot illustrated but are well known generally by those having ordinaryskill in the art.

In one implementation, the wireless communication system 100 iscompliant with NR protocols standardized in third generation partnershipproject (“3GPP”), wherein the network unit 104 transmits using an OFDMmodulation scheme on the downlink (“DL”) and the remote units 102transmit on the uplink (“UL”) using a single-carrier frequency divisionmultiple access (“SC-FDMA”) scheme or an orthogonal frequency divisionmultiplexing (“OFDM”) scheme. More generally, however, the wirelesscommunication system 100 may implement some other open or proprietarycommunication protocol, for example, WiMAX, institute of electrical andelectronics engineers (“IEEE”) 802.11 variants, global system for mobilecommunications (“GSM”), general packet radio service (“GPRS”), universalmobile telecommunications system (“UMTS”), long term evolution (“LTE”)variants, code division multiple access 2000 (“CDMA2000”), Bluetooth®,ZigBee, Sigfoxx, among other protocols. The present disclosure is notintended to be limited to the implementation of any particular wirelesscommunication system architecture or protocol.

The network units 104 may serve a number of remote units 102 within aserving area, for example, a cell or a cell sector via a wirelesscommunication link. The network units 104 transmit DL communicationsignals to serve the remote units 102 in the time, frequency, and/orspatial domain.

In various embodiments, a remote unit 102 may access a sidelinkdiscontinuous reception configuration. The sidelink discontinuousreception configuration corresponds to: a quality of service class; anidentifier of the quality of service class; at least one attribute ofthe quality of service class; a range corresponding to the at least oneattribute of the quality of service class; or some combination thereof.In some embodiments, the remote unit 102 may perform sidelinkcommunication based on the sidelink discontinuous receptionconfiguration. Accordingly, the remote unit 102 may be used for sidelinkdiscontinuous reception configuration.

In certain embodiments, a remote unit 102 may determine, at a first userequipment, at least one parameter for a sidelink discontinuous receptionconfiguration. In some embodiments, the remote unit 102 may transmit theat least one parameter for the sidelink discontinuous receptionconfiguration to a second user equipment. In certain embodiments, theremote unit 102 may receive feedback from the second user equipmentindicating acceptance of the at least one parameter for the sidelinkdiscontinuous reception configuration. Accordingly, the remote unit 102may be used for sidelink discontinuous reception configuration.

In various embodiments, a remote unit 102 may access a sidelinkdiscontinuous reception configuration. The sidelink discontinuousreception configuration includes a first offset for an on-duration, anon-duration timer, and a periodicity. In some embodiments, the remoteunit 102 may determine a second offset for the on-duration. In certainembodiments, the remote unit 102 may transmit data based on the sidelinkdiscontinuous reception configuration and the second offset for theon-duration. Accordingly, the remote unit 102 may be used for sidelinkdiscontinuous reception configuration.

In certain embodiments, a remote unit 102 may access a sidelinkdiscontinuous reception configuration. The sidelink discontinuousreception configuration includes an offset for an on-duration, anon-duration timer, and a periodicity. In some embodiments, the remoteunit 102 may transmit sidelink data, receive the sidelink data, or acombination thereof. In certain embodiments, the remote unit 102 may, inresponse to transmitting the sidelink data, receiving the sidelink data,or a combination thereof, start a sidelink inactivity timer. In variousembodiments, the remote unit 102 may restart the sidelink inactivitytimer in response to: indicating a negative acknowledgement on aphysical uplink control channel to request a retransmission grant to abase station; indicating an acknowledgement on the physical uplinkcontrol channel and in response to having a non-empty sidelink buffer tothe base station; receiving hybrid automatic repeat request feedback ona physical sidelink feedback channel from a sidelink receiver userequipment; transmitting a sidelink scheduling request to a base station;transmitting a sidelink buffer status report to the base station;requesting a channel state information report on sidelink from a peeruser equipment; receiving a request for a channel state informationreport on sidelink from a peer user equipment; receiving sidelinkcontrol information from the sidelink transmitter user equipment;receiving data from the sidelink transmitter user equipment;transmitting a physical sidelink feedback channel negativeacknowledgement feedback to the sidelink transmitter user equipment;transmitting sidelink control information requesting sidelink physicalsidelink feedback channel feedback; transmitting non-last sidelinkcontrol information while performing blind re-transmissions;transmitting non-last data while performing blind re-transmissions; async source using a value of a sidelink inactivity timer greater than apredetermined value; or some combination thereof. Accordingly, theremote unit 102 may be used for sidelink discontinuous receptionconfiguration.

FIG. 2 depicts one embodiment of an apparatus 200 that may be used forsidelink discontinuous reception configuration. The apparatus 200includes one embodiment of the remote unit 102. Furthermore, the remoteunit 102 may include a processor 202, a memory 204, an input device 206,a display 208, a transmitter 210, and a receiver 212. In someembodiments, the input device 206 and the display 208 are combined intoa single device, such as a touchscreen. In certain embodiments, theremote unit 102 may not include any input device 206 and/or display 208.In various embodiments, the remote unit 102 may include one or more ofthe processor 202, the memory 204, the transmitter 210, and the receiver212, and may not include the input device 206 and/or the display 208.

The processor 202, in one embodiment, may include any known controllercapable of executing computer-readable instructions and/or capable ofperforming logical operations. For example, the processor 202 may be amicrocontroller, a microprocessor, a central processing unit (“CPU”), agraphics processing unit (“GPU”), an auxiliary processing unit, a fieldprogrammable gate array (“FPGA”), or similar programmable controller. Insome embodiments, the processor 202 executes instructions stored in thememory 204 to perform the methods and routines described herein. Theprocessor 202 is communicatively coupled to the memory 204, the inputdevice 206, the display 208, the transmitter 210, and the receiver 212.

The memory 204, in one embodiment, is a computer readable storagemedium. In some embodiments, the memory 204 includes volatile computerstorage media. For example, the memory 204 may include a RAM, includingdynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/or staticRAM (“SRAM”). In some embodiments, the memory 204 includes non-volatilecomputer storage media. For example, the memory 204 may include a harddisk drive, a flash memory, or any other suitable non-volatile computerstorage device. In some embodiments, the memory 204 includes bothvolatile and non-volatile computer storage media. In some embodiments,the memory 204 also stores program code and related data, such as anoperating system or other controller algorithms operating on the remoteunit 102.

The input device 206, in one embodiment, may include any known computerinput device including a touch panel, a button, a keyboard, a stylus, amicrophone, or the like. In some embodiments, the input device 206 maybe integrated with the display 208, for example, as a touchscreen orsimilar touch-sensitive display. In some embodiments, the input device206 includes a touchscreen such that text may be input using a virtualkeyboard displayed on the touchscreen and/or by handwriting on thetouchscreen. In some embodiments, the input device 206 includes two ormore different devices, such as a keyboard and a touch panel.

The display 208, in one embodiment, may include any known electronicallycontrollable display or display device. The display 208 may be designedto output visual, audible, and/or haptic signals. In some embodiments,the display 208 includes an electronic display capable of outputtingvisual data to a user. For example, the display 208 may include, but isnot limited to, a liquid crystal display (“LCD”), a light emitting diode(“LED”) display, an organic light emitting diode (“OLED”) display, aprojector, or similar display device capable of outputting images, text,or the like to a user. As another, non-limiting, example, the display208 may include a wearable display such as a smart watch, smart glasses,a heads-up display, or the like. Further, the display 208 may be acomponent of a smart phone, a personal digital assistant, a television,a table computer, a notebook (laptop) computer, a personal computer, avehicle dashboard, or the like.

In certain embodiments, the display 208 includes one or more speakersfor producing sound. For example, the display 208 may produce an audiblealert or notification (e.g., a beep or chime). In some embodiments, thedisplay 208 includes one or more haptic devices for producingvibrations, motion, or other haptic feedback. In some embodiments, allor portions of the display 208 may be integrated with the input device206. For example, the input device 206 and display 208 may form atouchscreen or similar touch-sensitive display. In other embodiments,the display 208 may be located near the input device 206.

In some embodiments, the processor 202: accesses a sidelinkdiscontinuous reception configuration, wherein the sidelinkdiscontinuous reception configuration corresponds to: a quality ofservice class; an identifier of the quality of service class; at leastone attribute of the quality of service class; a range corresponding tothe at least one attribute of the quality of service class; or somecombination thereof; and performs sidelink communication based on thesidelink discontinuous reception configuration.

In certain embodiments, the processor 202 determines at least oneparameter for a sidelink discontinuous reception configuration. Invarious embodiments, the transmitter 210 transmits the at least oneparameter for the sidelink discontinuous reception configuration to asecond user equipment. In certain embodiments, the receiver 212 receivesfeedback from the second user equipment indicating acceptance of the atleast one parameter for the sidelink discontinuous receptionconfiguration.

In various embodiments, the processor 202: accesses a sidelinkdiscontinuous reception configuration, wherein the sidelinkdiscontinuous reception configuration comprises a first offset for anon-duration, an on-duration timer, and a periodicity; and determines asecond offset for the on-duration. In various embodiments, thetransmitter 210 transmits data based on the sidelink discontinuousreception configuration and the second offset for the on-duration.

In certain embodiments, the processor 202 accesses a sidelinkdiscontinuous reception configuration. The sidelink discontinuousreception configuration includes an offset for an on-duration, anon-duration timer, and a periodicity. In various embodiments, thetransmitter 210 transmits sidelink data, the receiver 212 receives thesidelink data, or a combination thereof. In response to the transmitter210 transmitting sidelink data, the receiver 212 receiving the sidelinkdata, or a combination thereof, the processor 202 starts a sidelinkinactivity timer. The processor 202 restarts the sidelink inactivitytimer in response to: indicating a negative acknowledgement on aphysical uplink control channel to request a retransmission grant to abase station; indicating an acknowledgement on the physical uplinkcontrol channel and in response to having a non-empty sidelink buffer tothe base station; receiving hybrid automatic repeat request feedback ona physical sidelink feedback channel from a sidelink receiver userequipment; transmitting a sidelink scheduling request to a base station;transmitting a sidelink buffer status report to the base station;requesting a channel state information report on sidelink from a peeruser equipment; receiving a request for a channel state informationreport on sidelink from a peer user equipment; receiving sidelinkcontrol information from the sidelink transmitter user equipment;receiving data from the sidelink transmitter user equipment;transmitting a physical sidelink feedback channel negativeacknowledgement feedback to the sidelink transmitter user equipment;transmitting sidelink control information requesting sidelink physicalsidelink feedback channel feedback; transmitting non-last sidelinkcontrol information while performing blind re-transmissions;transmitting non-last data while performing blind re-transmissions; async source using a value of a sidelink inactivity timer greater than apredetermined value; or some combination thereof.

Although only one transmitter 210 and one receiver 212 are illustrated,the remote unit 102 may have any suitable number of transmitters 210 andreceivers 212. The transmitter 210 and the receiver 212 may be anysuitable type of transmitters and receivers. In one embodiment, thetransmitter 210 and the receiver 212 may be part of a transceiver.

FIG. 3 depicts one embodiment of an apparatus 300 that may be used forsidelink discontinuous reception configuration. The apparatus 300includes one embodiment of the network unit 104. Furthermore, thenetwork unit 104 may include a processor 302, a memory 304, an inputdevice 306, a display 308, a transmitter 310, and a receiver 312. As maybe appreciated, the processor 302, the memory 304, the input device 306,the display 308, the transmitter 310, and the receiver 312 may besubstantially similar to the processor 202, the memory 204, the inputdevice 206, the display 208, the transmitter 210, and the receiver 212of the remote unit 102, respectively.

In certain embodiments, a discontinuous reception (“DRX”) configurationmay be brought to a vehicle to everything (“V2X”) layer (e.g., insteadof at an access stratum layer). Such embodiments may cause a duplicationof work (e.g., specification, implementation, and testing).

In some embodiments, a standard sidelink (“SL”) on-duration may be used.A standard SL on-duration may start at a known point in time and a SLuser equipment (“UE”) may remain active until a known timer (e.g.,on-duration-timer) is running. The standard SL on-duration may start ata fixed time offset (e.g., offset_std_On-duration) from Time_0 based ona synchronization source from global navigation satellite system(“GNSS”) or gNB directly or indirectly from sidelink synchronizationsignals (“SLSS”). The on-duration-timer may be restarted periodicallywith a periodicity. It should be noted that the term “active time” mayrefer to a time period where a SL UE transmits and receives data on a UEto UE interface (“PC5”) interface. This is different than a UE tonetwork interface (“Uu”) interface active time which only refers to atime period in which a UE is monitoring physical downlink controlchannel (“PDCCH”). In various embodiments, a SL-DRX-configuration isdefined as a combination of offset_std_On-duration, On-duration-timer,and periodicity as shown in FIG. 4 , and may be: 1) known universally(e.g., by way of specification); 2) known per application and/orapplication type; 3) known per service and/or service type; 4) known perquality of service (“QoS”) class (e.g., QoS class identifier (“QCI”),performance quality index (“PQI”), etc.); 5) known per one or moreattribute of a QoS class (e.g., QCI, PQI, etc.); and/or 6) known perrange of one or more attribute of a QoS class (e.g., QCI, PQI, etc.).

FIG. 4 is a timing diagram 400 illustrating one embodiment of a SL DRXconfiguration. The timing diagram 400 illustrates timing from Time_0 402over time 404, an offset_std_On-duration 406, a periodicity 408, and anOn-duration-timer 410.

In a first example, a first SL DRX configuration (e.g.,SL-DRX-configuration_1) is for basic safety messages and a second SL DRXconfiguration (e.g., SL-DRX-configuration_2) is for advanced safetymessages in V2X communication.

In a second example, a first SL DRX configuration (e.g.,SL-DRX-configuration_1) is for vehicular communication and a second SLDRX configuration (e.g., SL-DRX-configuration_) is for public safetyrelated communication.

In a third example, a first SL DRX configuration (e.g.,SL-DRX-configuration_1) is for pedestrian (e.g., vulnerable road user(“VRU”)) and a second SL DRX configuration (e.g.,SL-DRX-configuration_2) is vehicular messages in V2X communication.

In a fourth example, a first SL DRX configuration (e.g.,SL-DRX-configuration_1) is for a first PQI range (e.g., x1 to y1) and asecond SL DRX configuration (e.g., SL-DRX-configuration_2) is for asecond PQI range (e.g., x2 to y2).

In a fifth example, a first SL DRX configuration (e.g.,SL-DRX-configuration_1) is for a first QCI range (e.g., x1 to y1) and asecond SL DRX configuration (e.g., SL-DRX-configuration_2) is for asecond PQI range (e.g., x2 to y2).

In a sixth example, only one single SL DRX configuration (e.g.,SL-DRX-configuration_1) is used for any kind of sidelink communicationusing DRX based power savings.

FIG. 5 is a timing diagram 500 illustrating one embodiment of two SL DRXconfigurations corresponding to a first PQI range and a second PQIrange. The timing diagram 500 illustrates timing from Time_0 502 overtime 504 for a SL DRX configuration corresponding to a first PQI-range,an offset_std_On-duration 506, a periodicity 508, and anOn-duration-timer 510. The timing diagram 500 also illustrates timingfrom the Time_0 502 over time 516 for a SL DRX configurationcorresponding to a second PQI-range, an offset_std_On-duration 518, aperiodicity 520, and an On-duration-timer 522.

In various embodiments, not all SL DRX configuration parameters need tobe unique across different (e.g., all) SL DRX configurations.Accordingly, in such embodiments, one or two of the parametersoffset_std_On-duration, On-duration-timer, and periodicity may have acommon value across different (e.g., all) SL DRX configurations. Fordifferent SL DRX configurations, it is sufficient to have just one ortwo parameters different across the different SL DRX configurations. Forexample, the On-duration-timer may be small (e.g., some milliseconds)for applications with a small periodical data. As another example, theOn-duration-timer may be large (e.g., approaching infinity) for highlatency sensitive applications—as long as the application remains live.

In certain embodiments, instead of fixed values for a SL DRXconfiguration in a specification, the values for the SL DRXconfiguration may be configurable and indicated to a UE using non-accessstratum (“NAS”) or radio resource configuration (“RRC”) signaling wherean application management function (“AMF”) or a gNB lets a SL UE knowthe SL DRX configuration for its geographical area like a radio accessnetwork (“RAN”) based notification area, UE's registration area (e.g.,timing advance (“TA”) list), just cell areas, and/or just trackingareas. Preconfiguration of a SL DRX configuration may also be done.

In some embodiments, one or more SL DRX configurations between a pair ofpeer UEs in a unicast connection may be aligned. In such embodiments,one of the peer UEs may negotiate an On-duration start time (e.g.,offset_common_On-duration) different from a offset_std_On-duration toalign and/or overlap with one or more existing On-durations—so, a UE mayrequest its peer UE to move the On-duration start time to aoffset_common_On-duration. The negotiation may be done using PC5, NAS,or RRC signaling.

FIG. 6 is a network communications 600 diagram illustrating oneembodiment of a negotiation of SL DRX configuration for unicastcommunication. The communications 600 are illustrated between a first SLUE 602 and a second SL UE 604. Each of the communications 600 mayinclude one or more messages.

In a first communication 606, the first SL UE 602 transmits a SL DRXreconfiguration message (e.g., new offset_common_On-duration) to thesecond SL UE 604. In a second communication 608, the second SL UE 604transmits a SL DRX reconfiguration complete message to the first SL UE602. In a third communication 610, the new SL DRX configuration isapplied to the first SL UE 602 and the second SL UE 604.

Specifically, as illustrated in FIG. 6 , having started a unicastcommunication for a certain service according to its corresponding knownSL DRX configuration, the first SL UE 602 aligns a SL DRX configurationwith other SL DRX configurations to enable maximizing of its sleep time.

In some embodiments, alignment of On-durations between a group of UEs ina groupcast communication is used as shown in FIG. 7 where all groupmembers at a moment communicate using one or more standard known SL DRXconfigurations. In such embodiments, one group member (e.g., a groupleader) realizes opportunity for further power saving (e.g., realizesthat there are more than one SL DRX configurations in use) and the groupmember requests that other group members (e.g., using a reconfigurationquery) move to a different On-duration starting time calledoffset_common_On-duration. The reconfiguration query may be sent using agroupcast (“GC”) signaling (e.g., addressed to a layer 2 (“L2”) GCdestination identifier (“ID”)). The offset_common_On-duration may be oneof the offset_std_On-durations. In such embodiments, the group membersmay respond with a reconfiguration accept or a reconfigurationreject—that may be sent in a unicast (“UC”) manner to the initiatinggroup member (e.g., to the group leader) or in a GC manner to the allgroup members. A reconfiguration reject sent by any member UE may leadto a negotiation failure or a new offset_common_On-duration may need tobe negotiated. The initiating group member (e.g., the group leader) mayannounce actual reconfiguration of the SL DRX configurations.

In various embodiments, in a time-optimized implementation, groupmembers (e.g., an initiating group member such as a group leader)announce reconfiguration of SL DRX configurations.

In certain embodiments, an offset_common_On-duration is advertised foreach and/or any offset_std_On-duration relevant for communicationrelevant to a group—this helps a new group member to find theoffset_common_On-duration. The offset_common_On-duration may beadvertised by a group member (e.g., group leader) or by a roadside unit(“RSU”).

In some embodiments, a request and/or negotiation as shown in FIG. 8 maybe done using NAS, RRC, or lower layer signaling. In variousembodiments, if more than one UE triggers and/or sends a reconfigurationquery: 1) the reconfiguration query that arrives later may be ignored bya group member; 2) a reconfiguration query from a UE with a smaller (orlarger) member ID may be accepted; or 3) only a group leader can send areconfiguration query.

FIG. 7 is a network communications 700 diagram illustrating oneembodiment of a negotiation of SL DRX configuration for groupcastcommunication. The communications 700 are illustrated between a first SLUE 702, a second SL UE 704, a third SL UE 706, and an Nth SL UE 708.Each of the communications 700 may include one or more messages.

In a first communication 710, each of the first SL UE 702, the second SLUE 704, the third SL UE 706, and the Nth SL UE 708 group of UEs mayfollow a default SL DRX configuration. In a second communication 712, athird communication 714, and a fourth communication 716, the first SL UE702 transmits a reconfiguration query message (e.g., newoffset_common_On-duration) to the second SL UE 704, the third SL UE 706,and the Nth SL UE 708. In a fifth communication 718, a sixthcommunication 720, and a seventh communication 722, the second SL UE704, the third SL UE 706, and the Nth SL UE 708 respectively transmit areconfiguration accept message to the first SL UE 702. In an eighthcommunication 724, a ninth communication 726, and a tenth communication728, the first SL UE 702 transmits a reconfiguration message (e.g., newoffset_std_On-duration) to the second SL UE 704, the third SL UE 706,and the Nth SL UE 708. In an eleventh communication 730, the new SL DRXconfiguration is applied to the first SL UE 702, the second SL UE 704,the third SL UE 706, and the Nth SL UE 708.

In certain embodiments, an offset_common_On-duration is randomly pickedfrom a set of offset values to facilitate proper resource utilization.The set of offset values may be configured, preconfigured, or specified.A possible configuration of the set of offset values may be achievedusing RRC signaling, NAS signaling, or the set of offset values may beprovided by the V2X layer.

In some embodiments, a SL DRX configuration is done in a manner similarto sidelink resource block (“SLRB”) configuration. This may beapplicable for a unicast, a groupcast, and a broadcast connection.Further, this may be applicable to: 1) Mode 1: dedicated DRXconfigurations; and 2) Mode 2: broadcast DRX configurations (orpre-configured).

In various embodiments, a SL DRX configuration may be achieved byconfiguring resource pools such that SL resources are available onlyperiodically. A UE may sleep in time periods where there are no SLresources available and may wake up on certain time occasionsperiodically if the SL resources again become available, to be able touse the SL resources for transmission and reception.

In certain embodiments, any reconfiguration of a SL resource may be donein advance and communicated to UEs accordingly. This may be doneusing: 1) a longer modification period—each modification period maycontain more than one occasion of SL resources; or 2) thereconfiguration may only be carried out after ‘N’ modification periods.In some embodiments, SL resource pools may be given (e.g., by way ofpreconfiguration or specification). In such embodiments, the resourcepools may not change or get reconfigured. The UE assumes that thetransmission and reception time are according to known SL resource poolconfigurations and therefore may sleep if SL resources are notavailable.

One embodiment of a configuration of a resource pool using a sidelinkresource pool information element (“IE”) is illustrated in Table 1.

TABLE 1 Sidelink Resource Pool IE -- ASNISTART --TAG-SL-RESOURCEPOOL-START SL-ResourcePool-r16 ::= SEQUENCE { sl-PSCCH-Config-r16  SetupRelease { SL-PSCCH-Config-r16 }      OPTIONAL,  -- Need M  sl-PSSCH-Config-r16  SetupRelease {SL-PSSCH-Config-r16 }       OPTIONAL,  -- Need M  sl-PSFCH-Config-r16 SetupRelease { SL-PSFCH-Config-r16 }       OPTIONAL,  -- Need M  sl-offset_std_On-duration     INTEGER (0..1024*5)  OPTIONAL,  sl-On-duration-timer         ENUMERATED {ms2, ms20, ms200, infinite} OPTIONAL,   sl-Periodicity         ENUMERATED {one-fourth, half, one,two}  OPTIONAL,  sl-SyncAllowed-r16 SL-SyncAllowed-r16   OPTIONAL, --Need M  sl-SubchannelSize-r16  ENUMERATED {n10, n12, n15, n20, n25, n50,n75, n100} OPTIONAL, -- Need M  sl-TimeResource-r16 INTEGER (10..160)  OPTIONAL, -- Need M  sl-StartRB-Subchannel-r16  INTEGER (0..265)   OPTIONAL, -- Need M  sl-NumSubchannel-r16 INTEGER (1..27)   OPTIONAL,-- Need M  sl-Additional-MCS-Table-r16     ENUMERATED { qam256,qam64LowSE, qam256-qam64LowSE } OPTIONAL, -- Need M sl-ThreshS-RSSI-CBR-r16 INTEGER (0..45)    OPTIONAL, -- Need M  sl-TimeWindowSizeCBR-r16  ENUMERATED {ms100, slot100} OPTIONAL, -- Need M sl-Time WindowSizeCR-r16  ENUMERATED {ms1000, slot1000} OPTIONAL, --Need M  sl-PTRS-Config-r16 SL-PTRS-Config-r16   OPTIONAL, -- Need M sl-UE-SelectedConfigRP-r16  SL-UE-SelectedConfigRP-r16       OPTIONAL,Need M  sl-RxParametersNcell-r16 SEQUENCE {   sl-TDD-Configuration-r16    TDD-UL-DL-ConfigCommon       OPTIONAL, -- Need M  sl-SyncConfigIndex-r16 INTEGER (0..15)  }               OPTIONAL, --Need M  sl-ZoneConfigMCR-List-r16 SEQUENCE (SIZE (16)) OFSL-ZoneConfigMCR-r16 OPTIONAL, -- Need M  sl-FilterCoefficient-r16 FilterCoefficient OPTIONAL, -- Need M sl-RB-Number-r16 INTEGER(10..275)  OPTIONAL, -- Need M  sl-PreemptionEnable-r16   ENUMERATED{enabled, pl1, pl2, pl3, pl4, pl5, pl6, pl7, pl8} OPTIONAL, -- Need Rsl-Priority Threshold-UL-URLLC-r16  INTEGER (1..9)     OPTIONAL, -- NeedM sl-Priority Threshold-r16  INTEGER (1..9) OPTIONAL, -- Need Msl-X-Overhead-r16 ENUMERATED {n0,n3, n6, n9}     OPTIONAL, -- Need M sl-PowerControl-r16 SL-PowerControl-r16    OPTIONAL, -- Need Msl-TxPercentageList-r16 SL-TxPercentageList-r16 OPTIONAL, -- Need Msl-MinMaxMCS-List-r16  SL-MinMaxMCS-List-r16    OPTIONAL, -- Need M }

In some embodiments, a half-duplex (“HD”) issue may exist if multipleUEs buffering data for transmission attempt to transmit simultaneouslyat a start of a DRX On-duration.

In various embodiments, to avoid the HD issue, at least onere-transmission may be made for which a time of re-transmission ischosen randomly from a time window starting at an offset after atransmission has been made. The time window may be preconfigured,configured, or specified.

In certain embodiments, to avoid the HD issue, each member (e.g., in UCor GC) transmits in a round-robin fashion once an On-duration-timer isstarted. For example, a first member transmits in a first slot, a secondmember transmits in a second slot, and so forth. In such embodiments, atleast one transmission is made by each member even if just to notifythat there is no-data-available. The notification of no-data-availablemay be done using a medium access control (“MAC”) control element(“CE”), physical layer sidelink control information (“SCI”), or othersignaling. Moreover, if a number of transmitters and/or transmittermembers in a group is known from a higher layer for a groupcast thenonly transmitter UEs transmit in the round robin manner.

In some embodiments, a SL UE requests that a serving gNB align a Uu DRXcycle according to its SL DRX configuration. The SL UE sends UE assistedinformation (“UAI”) to the gNB, as shown in FIG. 8 , signaling SL DRXconfiguration parameters (e.g., offset_std_On-duration,On-duration-timer, and periodicity) and: 1) the gNB may send back a UuDRX configuration (e.g., RRCReconfiguration) that maximizes overlap of aUu and a SL active time for the SL UE; 2) the gNB may send back a Uu DRXconfiguration (e.g., RRCReconfiguration) that does not necessarilymaximize overlap of the Uu and the SL active time but rather attempts toaverage out system load and/or resource efficiency; or 3) the gNB maysend back a Uu DRX configuration (e.g., RRCReconfiguration) thatachieves a balance between the above two options.

FIG. 8 is a network communications 800 diagram illustrating oneembodiment of Uu negotiation to align Uu and SL DRX. The communications800 are illustrated between a UE 802 and a network 804. Each of thecommunications 800 may include one or more messages.

In a first communication 806, the UE 802 transmits UE assistanceinformation (e.g., part of SL DRX configuration) to the network 804. Ina second communication 808, the network 804 transmits anRRCReconfiguration message to the UE 802. The UE 802 applies thereceived Uu DRX configuration (e.g., RRCReconfiguration).

In various embodiments, a SL UE, upon transmitting or receiving data,may start and/or restart a SL inactivity timer (e.g.,SL-inactivity-timer). If both the On-duration-timer (e.g., on durationtimer) and the SL-inactivity-timer expire, the SL UE enters DRX sleep asshown in FIG. 9 . The SL-inactivity-timer may also be started and/orrestarted at one or more of the following occasions: 1) when indicatinga negative acknowledgement (“NACK”) on a physical uplink control channel(“PUCCH”) to request a re-transmission grant; 2) when indicating anacknowledgement (“ACK”) on a PUCCH and having a non-empty SL buffer; 3)when it receives hybrid automatic repeat request (“HARQ”) feedback on aphysical sidelink feedback channel (“PSFCH”); 4) when transmitting a SLscheduling request (“SR”) (“SL-SR”) and/or a SL buffer status report(“BSR”) (“SL-BSR”) to a gNB; 5) when requesting a channel stateinformation (“CSI”) report on SL from a peer UE; 6) when having receiveda request for a CSI-report on SL from a peer UE; 7) when receiving SCI(e.g., PUCCH) which may contain a relevant source (“SRC”) layer 2identifier (“L2ID”) and/or destination (“DST”) L2ID; 8) when receivingdata (e.g., PSSCH); 9) when sending a PSFCH NACK feedback; 10) whentransmitting SCI (e.g., PSCCH) requesting SL PSFCH feedback; 11) whentransmitting non-last SCI (e.g., PSCCH) for blind re-transmissions; 12)when transmitting non-last data (e.g., PSSCH) for blindre-transmissions; and/or 13) a synchronization source uses an infinite(or very long) value of a SL-inactivity-timer.

FIG. 9 is a timing diagram 900 illustrating one embodiment of SL DRXinterplay with timers. The timing diagram 900 illustrates a sleep time902, a start 904 of an On-duration-timer, a time to wake-up 906, anevent 908 triggering the start and/or restart of a SL-inactivity-timer,a start 910 of the SL-inactivity-timer, an expiration 912 of theOn-duration-timer, and an expiration 914 of the SL-inactivity-timer.

In some embodiments, a resource pool configuration (e.g., from anetwork) and usage (e.g., from a UE) may be different for thefollowing: 1) resource pool specific DRX: every resource pool has aconfigured SL DRX configuration—a SL UE chooses the SL DRX configurationaccording to its power saving needs and frequency of data transmissionand/or reception for serving periodic applications; and 2) separateresource pools for vehicular traffic, for pedestrian UEs, for publicsafety, and/or for commercial SL UEs. In one example, a pedestrian(e.g., VRU) UE interested only in communicating with other pedestrian(e.g., VRU) UEs may use only a corresponding resource pool to receiveand transmit messages. A vehicular UE may only transmit to pedestrian(e.g., VRU) UEs in that resource pool.

FIG. 10 is a flow chart diagram illustrating one embodiment of a method1000 for sidelink discontinuous reception configuration. In someembodiments, the method 1000 is performed by an apparatus, such as theremote unit 102. In certain embodiments, the method 1000 may beperformed by a processor executing program code, for example, amicrocontroller, a microprocessor, a CPU, a GPU, an auxiliary processingunit, a FPGA, or the like.

In various embodiments, the method 1000 includes accessing 1002 asidelink discontinuous reception configuration. The sidelinkdiscontinuous reception configuration corresponds to: a quality ofservice class; an identifier of the quality of service class; at leastone attribute of the quality of service class; a range corresponding tothe at least one attribute of the quality of service class; or somecombination thereof. In some embodiments, the method 1000 includesperforming 1004 sidelink communication based on the sidelinkdiscontinuous reception configuration.

In certain embodiments, the sidelink discontinuous receptionconfiguration comprises an offset from a fixed time reference for anon-duration, an on-duration timer, a periodicity, or some combinationthereof. In some embodiments, the method 1000 further comprisesreceiving information indicating the offset for the on-duration, theon-duration timer, the periodicity, or some combination thereof.

In various embodiments, the information indicating the offset for theon-duration, the on-duration timer, the periodicity, or some combinationthereof is received via non-access stratum signaling or radio resourcecontrol signaling. In one embodiment, the quality of service classcomprises a quality of service class identifier for sidelinkcommunication.

FIG. 11 is a flow chart diagram illustrating another embodiment of amethod 1100 for sidelink discontinuous reception configuration. In someembodiments, the method 1100 is performed by an apparatus, such as theremote unit 102. In certain embodiments, the method 1100 may beperformed by a processor executing program code, for example, amicrocontroller, a microprocessor, a CPU, a GPU, an auxiliary processingunit, a FPGA, or the like.

In various embodiments, the method 1100 includes determining 1102, at afirst user equipment, at least one parameter for a sidelinkdiscontinuous reception configuration. In some embodiments, the method1100 includes transmitting 1104 the at least one parameter for thesidelink discontinuous reception configuration to a second userequipment. In certain embodiments, the method 1100 includes receiving1106 feedback from the second user equipment indicating acceptance ofthe at least one parameter for the sidelink discontinuous receptionconfiguration.

In certain embodiments, the method 1100 further comprises communicatingwith the second user equipment based on the sidelink discontinuousreception configuration. In some embodiments, the at least one parametercomprises an offset for an on-duration, an on-duration timer, aperiodicity, or some combination thereof. In various embodiments,determining the at least one parameter for the sidelink discontinuousreception configuration comprises determining a change to the at leastone parameter from a prior sidelink discontinuous receptionconfiguration used by the first user equipment and the second userequipment.

In one embodiment, the at least one parameter for the sidelinkdiscontinuous reception configuration is transmitted to the second userequipment using a sidelink interface, non-access stratum signaling, orsidelink radio resource control signaling. In certain embodiments,determining the at least one parameter for the sidelink discontinuousreception configuration is based on information received from a networkdevice for the first user equipment to the network device discontinuousreception alignment or based on a time at which there is data availablefor transmission.

FIG. 12 is a flow chart diagram illustrating yet another embodiment of amethod 1200 for sidelink discontinuous reception configuration. In someembodiments, the method 1200 is performed by an apparatus, such as theremote unit 102. In certain embodiments, the method 1200 may beperformed by a processor executing program code, for example, amicrocontroller, a microprocessor, a CPU, a GPU, an auxiliary processingunit, a FPGA, or the like.

In various embodiments, the method 1200 includes accessing 1202 asidelink discontinuous reception configuration. The sidelinkdiscontinuous reception configuration includes a first offset for anon-duration, an on-duration timer, and a periodicity. In someembodiments, the method 1200 includes determining 1204 a second offsetfor the on-duration. In certain embodiments, the method 1200 includestransmitting 1206 data based on the sidelink discontinuous receptionconfiguration and the second offset for the on-duration.

In certain embodiments, the data is transmitted at a time after thestart of the on-duration timer that is offset by the second offset forthe on-duration. In some embodiments, the method 1200 further comprisesretransmitting the data at a second offset, wherein the second offset israndomly from a set of values. In various embodiments, the second offsetfor the on-duration is determined based on a number of user equipmentstransmitting data.

FIG. 13 is a flow chart diagram illustrating a further embodiment of amethod 1300 for sidelink discontinuous reception configuration. In someembodiments, the method 1300 is performed by an apparatus, such as theremote unit 102. In certain embodiments, the method 1300 may beperformed by a processor executing program code, for example, amicrocontroller, a microprocessor, a CPU, a GPU, an auxiliary processingunit, a FPGA, or the like.

In various embodiments, the method 1300 includes accessing 1302 asidelink discontinuous reception configuration. The sidelinkdiscontinuous reception configuration includes an offset for anon-duration, an on-duration timer, and a periodicity. In someembodiments, the method 1300 includes transmitting 1304 sidelink data,receiving the sidelink data, or a combination thereof. In certainembodiments, the method 1300 includes, in response to transmitting thesidelink data, receiving 1306 the sidelink data, or a combinationthereof, starting a sidelink inactivity timer. In various embodiments,the method 1300 includes restarting 1308 the sidelink inactivity timerin response to: indicating a negative acknowledgement on a physicaluplink control channel to request a retransmission grant to a basestation; indicating an acknowledgement on the physical uplink controlchannel and in response to having a non-empty sidelink buffer to thebase station; receiving hybrid automatic repeat request feedback on aphysical sidelink feedback channel from a sidelink receiver userequipment; transmitting a sidelink scheduling request to a base station;transmitting a sidelink buffer status report to the base station;requesting a channel state information report on sidelink from a peeruser equipment; receiving a request for a channel state informationreport on sidelink from a peer user equipment; receiving sidelinkcontrol information from the sidelink transmitter user equipment;receiving data from the sidelink transmitter user equipment;transmitting a physical sidelink feedback channel negativeacknowledgement feedback to the sidelink transmitter user equipment;transmitting sidelink control information requesting sidelink physicalsidelink feedback channel feedback; transmitting non-last sidelinkcontrol information while performing blind re-transmissions;transmitting non-last data while performing blind re-transmissions; async source using a value of a sidelink inactivity timer greater than apredetermined value; or some combination thereof.

In certain embodiments, the method 1300 further comprises, in responseto the on-duration timer expiring and the sidelink inactivity timerexpiring, entering a sleep mode.

In one embodiment, a method comprises: accessing a sidelinkdiscontinuous reception configuration, wherein the sidelinkdiscontinuous reception configuration corresponds to: a quality ofservice class; an identifier of the quality of service class; at leastone attribute of the quality of service class; a range corresponding tothe at least one attribute of the quality of service class; or somecombination thereof; and performing sidelink communication based on thesidelink discontinuous reception configuration.

In certain embodiments, the sidelink discontinuous receptionconfiguration comprises an offset from a fixed time reference for anon-duration, an on-duration timer, a periodicity, or some combinationthereof.

In some embodiments, the method further comprises receiving informationindicating the offset for the on-duration, the on-duration timer, theperiodicity, or some combination thereof.

In various embodiments, the information indicating the offset for theon-duration, the on-duration timer, the periodicity, or some combinationthereof is received via non-access stratum signaling or radio resourcecontrol signaling.

In one embodiment, the quality of service class comprises a quality ofservice class identifier for sidelink communication.

In one embodiment, an apparatus comprises: a processor that: accesses asidelink discontinuous reception configuration, wherein the sidelinkdiscontinuous reception configuration corresponds to: a quality ofservice class; an identifier of the quality of service class; at leastone attribute of the quality of service class; a range corresponding tothe at least one attribute of the quality of service class; or somecombination thereof; and performs sidelink communication based on thesidelink discontinuous reception configuration.

In certain embodiments, the sidelink discontinuous receptionconfiguration comprises an offset from a fixed time reference for anon-duration, an on-duration timer, a periodicity, or some combinationthereof.

In some embodiments, the apparatus further comprises a receiver thatreceives information indicating the offset for the on-duration, theon-duration timer, the periodicity, or some combination thereof.

In various embodiments, the information indicating the offset for theon-duration, the on-duration timer, the periodicity, or some combinationthereof is received via non-access stratum signaling or radio resourcecontrol signaling.

In one embodiment, the quality of service class comprises a quality ofservice class identifier for sidelink communication.

In one embodiment, a method comprises: determining, at a first userequipment, at least one parameter for a sidelink discontinuous receptionconfiguration; transmitting the at least one parameter for the sidelinkdiscontinuous reception configuration to a second user equipment; andreceiving feedback from the second user equipment indicating acceptanceof the at least one parameter for the sidelink discontinuous receptionconfiguration.

In certain embodiments, the method further comprises communicating withthe second user equipment based on the sidelink discontinuous receptionconfiguration.

In some embodiments, the at least one parameter comprises an offset foran on-duration, an on-duration timer, a periodicity, or some combinationthereof.

In various embodiments, determining the at least one parameter for thesidelink discontinuous reception configuration comprises determining achange to the at least one parameter from a prior sidelink discontinuousreception configuration used by the first user equipment and the seconduser equipment.

In one embodiment, the at least one parameter for the sidelinkdiscontinuous reception configuration is transmitted to the second userequipment using a sidelink interface, non-access stratum signaling, orsidelink radio resource control signaling.

In certain embodiments, determining the at least one parameter for thesidelink discontinuous reception configuration is based on informationreceived from a network device for the first user equipment to thenetwork device discontinuous reception alignment or based on a time atwhich there is data available for transmission.

In one embodiment, an apparatus comprising a first user equipment. Theapparatus further comprises: a processor that determines at least oneparameter for a sidelink discontinuous reception configuration; atransmitter that transmits the at least one parameter for the sidelinkdiscontinuous reception configuration to a second user equipment; and areceiver that receives feedback from the second user equipmentindicating acceptance of the at least one parameter for the sidelinkdiscontinuous reception configuration.

In certain embodiments, the transmitter and the receiver communicatewith the second user equipment based on the sidelink discontinuousreception configuration.

In some embodiments, the at least one parameter comprises an offset foran on-duration, an on-duration timer, a periodicity, or some combinationthereof.

In various embodiments, the processor determining the at least oneparameter for the sidelink discontinuous reception configurationcomprises the processor determining a change to the at least oneparameter from a prior sidelink discontinuous reception configurationused by the first user equipment and the second user equipment.

In one embodiment, the at least one parameter for the sidelinkdiscontinuous reception configuration is transmitted to the second userequipment using a sidelink interface, non-access stratum signaling, orsidelink radio resource control signaling.

In certain embodiments, the processor determining the at least oneparameter for the sidelink discontinuous reception configuration isbased on information received from a network device for the first userequipment to the network device discontinuous reception alignment orbased on a time at which there is data available for transmission.

In one embodiment, a method comprises: accessing a sidelinkdiscontinuous reception configuration, wherein the sidelinkdiscontinuous reception configuration comprises a first offset for anon-duration, an on-duration timer, and a periodicity; determining asecond offset for the on-duration; and transmitting data based on thesidelink discontinuous reception configuration and the second offset forthe on-duration.

In certain embodiments, the data is transmitted at a time after thestart of the on-duration timer that is offset by the second offset forthe on-duration.

In some embodiments, the method further comprises retransmitting thedata at a second offset, wherein the second offset is randomly from aset of values.

In various embodiments, the second offset for the on-duration isdetermined based on a number of user equipments transmitting data.

In one embodiment, an apparatus comprises: a processor that: accesses asidelink discontinuous reception configuration, wherein the sidelinkdiscontinuous reception configuration comprises a first offset for anon-duration, an on-duration timer, and a periodicity; and determines asecond offset for the on-duration; and a transmitter that transmits databased on the sidelink discontinuous reception configuration and thesecond offset for the on-duration.

In certain embodiments, the data is transmitted at a time after thestart of the on-duration timer that is offset by the second offset forthe on-duration.

In some embodiments, the transmitter retransmits the data at a secondoffset, wherein the second offset is randomly from a set of values.

In various embodiments, the second offset for the on-duration isdetermined based on a number of user equipments transmitting data.

In one embodiment, a method comprises: accessing a sidelinkdiscontinuous reception configuration, wherein the sidelinkdiscontinuous reception configuration comprises an offset for anon-duration, an on-duration timer, and a periodicity; transmittingsidelink data, receiving the sidelink data, or a combination thereof; inresponse to transmitting the sidelink data, receiving the sidelink data,or a combination thereof, starting a sidelink inactivity timer; andrestarting the sidelink inactivity timer in response to: indicating anegative acknowledgement on a physical uplink control channel to requesta retransmission grant to a base station; indicating an acknowledgementon the physical uplink control channel and in response to having anon-empty is sidelink buffer to the base station; receiving hybridautomatic repeat request feedback on a physical sidelink feedbackchannel from a sidelink receiver user equipment; transmitting a sidelinkscheduling request to a base station; transmitting a sidelink bufferstatus report to the base station; requesting a channel stateinformation report on sidelink from a peer user equipment; receiving arequest for a channel state information report on sidelink from a peeruser equipment; receiving sidelink control information from the sidelinktransmitter user equipment; receiving data from the sidelink transmitteruser equipment; transmitting a physical sidelink feedback channelnegative acknowledgement feedback to the sidelink transmitter userequipment; transmitting sidelink control information requesting sidelinkphysical sidelink feedback channel feedback; transmitting non-lastsidelink control information while performing blind re-transmissions;transmitting non-last data while performing blind re-transmissions; async source using a value of a sidelink inactivity timer greater than apredetermined value; or some combination thereof.

In certain embodiments, the method further comprises, in response to theon-duration timer expiring and the sidelink inactivity timer expiring,entering a sleep mode.

In one embodiment, an apparatus comprises: a processor that accesses asidelink discontinuous reception configuration, wherein the sidelinkdiscontinuous reception configuration comprises an offset for anon-duration, an on-duration timer, and a periodicity; a transmitter; anda receiver, wherein the transmitter transmits sidelink data, thereceiver receives the sidelink data, or a combination thereof wherein:in response to the transmitter transmitting sidelink data, the receiverreceiving the sidelink data, or a combination thereof, the processorstarts a sidelink inactivity timer; the processor restarts the sidelinkinactivity timer in response to: indicating a negative acknowledgementon a physical uplink control channel to request a retransmission grantto a base station; indicating an acknowledgement on the physical uplinkcontrol channel and in response to having a non-empty sidelink buffer tothe base station; receiving hybrid automatic repeat request feedback ona physical sidelink feedback channel from a sidelink receiver userequipment; transmitting a sidelink scheduling request to a base station;transmitting a sidelink buffer status report to the base station;requesting a channel state information report on sidelink from a peeruser equipment; receiving a request for a channel state informationreport on sidelink from a peer user equipment; receiving sidelinkcontrol information from the sidelink transmitter user equipment;receiving data from the sidelink transmitter user equipment;transmitting a physical sidelink feedback channel negativeacknowledgement feedback to the sidelink transmitter user equipment;transmitting sidelink control information requesting sidelink physicalsidelink feedback channel feedback; transmitting non-last sidelinkcontrol information while performing blind re-transmissions;transmitting non-last data while performing blind re-transmissions; async source using a value of a sidelink inactivity timer greater than apredetermined value; or some combination thereof.

In certain embodiments, the processor, in response to the on-durationtimer expiring and the sidelink inactivity timer expiring, enters asleep mode.

Embodiments may be practiced in other specific forms. The describedembodiments are to be considered in all respects only as illustrativeand not restrictive. The scope of the invention is, therefore, indicatedby the appended claims rather than by the foregoing description. Allchanges which come within the meaning and range of equivalency of theclaims are to be embraced within their scope.

1. An apparatus comprising: a processor that: accesses a sidelinkdiscontinuous reception configuration, wherein the sidelinkdiscontinuous reception configuration corresponds to: a quality ofservice class; an identifier of the quality of service class; at leastone attribute of the quality of service class; or some combinationthereof; and performs sidelink communication based on the sidelinkdiscontinuous reception configuration.
 2. The apparatus of claim 1,wherein the sidelink discontinuous reception configuration comprises anon-duration timer, a periodicity, or some combination thereof.
 3. Theapparatus of claim 2, further comprising a receiver that receivesinformation indicating the offset for the on-duration, the on-durationtimer, the periodicity, or some combination thereof.
 4. The apparatus ofclaim 3, wherein the information indicating the offset for theon-duration, the on-duration timer, the periodicity, or some combinationthereof is received via non-access stratum signaling or radio resourcecontrol signaling.
 5. The apparatus of claim 1, wherein the quality ofservice class comprises a quality of service class identifier forsidelink communication.
 6. An apparatus comprising a first userequipment, the apparatus further comprises: a processor that determinesat least one parameter for a sidelink discontinuous receptionconfiguration; a transmitter that transmits the at least one parameterfor the sidelink discontinuous reception configuration to a second userequipment; and a receiver that receives feedback from the second userequipment indicating acceptance of the at least one parameter for thesidelink discontinuous reception configuration.
 7. The apparatus ofclaim 6, wherein the transmitter and the receiver communicate with thesecond user equipment based on the sidelink discontinuous receptionconfiguration.
 8. The apparatus of claim 6, wherein the at least oneparameter comprises an offset for an on-duration, an on-duration timer,a periodicity, or some combination thereof.
 9. The apparatus of claim 6,wherein the processor determining the at least one parameter for thesidelink discontinuous reception configuration comprises the processordetermining a change to the at least one parameter from a prior sidelinkdiscontinuous reception configuration used by the first user equipmentand the second user equipment.
 10. The apparatus of claim 6, wherein theat least one parameter for the sidelink discontinuous receptionconfiguration is transmitted to the second user equipment using asidelink interface, non-access stratum signaling, or sidelink radioresource control signaling.
 11. The apparatus of claim 6, wherein the atleast one parameter for the sidelink discontinuous receptionconfiguration is determined based on discontinuous reception alignmentinformation received from a network device.
 12. (canceled) 13.(canceled)
 14. (canceled)
 15. (canceled)
 16. An apparatus comprising: aprocessor that accesses a sidelink discontinuous receptionconfiguration, wherein the sidelink discontinuous receptionconfiguration comprises an offset for an on-duration, an on-durationtimer, and a periodicity; a transmitter; and a receiver, wherein thetransmitter transmits sidelink data, the receiver receives the sidelinkdata, or a combination thereof; wherein: in response to the transmittertransmitting sidelink data, the receiver receiving the sidelink data, ora combination thereof, the processor starts a sidelink inactivity timer;the processor restarts the sidelink inactivity timer in response to:indicating a negative acknowledgement on a physical uplink controlchannel to request a retransmission grant to a base station; indicatingan acknowledgement on the physical uplink control channel and inresponse to having a non-empty sidelink buffer to the base station;receiving hybrid automatic repeat request feedback on a physicalsidelink feedback channel from a sidelink receiver user equipment;transmitting a sidelink scheduling request to a base station;transmitting a sidelink buffer status report to the base station;requesting a channel state information report on sidelink from a peeruser equipment; receiving a request for a channel state informationreport on sidelink from a peer user equipment; receiving sidelinkcontrol information from the sidelink transmitter user equipment;receiving data from the sidelink transmitter user equipment;transmitting a physical sidelink feedback channel negativeacknowledgement feedback to the sidelink transmitter user equipment;transmitting sidelink control information requesting sidelink physicalsidelink feedback channel feedback; transmitting non-last sidelinkcontrol information while performing blind re-transmissions;transmitting non-last data while performing blind re-transmissions; async source using a value of a sidelink inactivity timer greater than apredetermined value; or some combination thereof.
 17. The apparatus ofclaim 16, wherein the processor, in response to the on-duration timerexpiring and the sidelink inactivity timer expiring, enters a sleepmode.